Service compliance enforcement using user activity monitoring and work request verification

ABSTRACT

A computer implemented method, data processing system, and computer program product control point in time access to a remote client device and auditing system logs of the remote client device by an auditing server device to determine whether monitored user activity on the remote client device associated with a work request was in compliance with one or more regulations.

This application claims the benefit of U.S. Provisional Application No.61/623,990, filed Apr. 13, 2012, the entirety of which is incorporatedby reference herein.

BACKGROUND

1. Field

The disclosure relates to a computer implemented method, data processingsystem, and computer program product for realtime capturing andmonitoring of remote activities using a client-side identificationmanagement agent.

2. Description of the Related Art

Network security is becoming more and more important as businesses,governmental agencies, medical institutions, financial institutions, andeducational institutions spend more and more time connected online toprovide services to individuals. Network security consists ofprovisions, policies, regulations, and laws designed to prevent andmonitor unauthorized access, misuse, or modification ofnetwork-accessible resources. Network security is the authorization ofaccess to resources within a network. Typically, users are assigned anidentification (identifiers), such as a user name, and a password thatallows the users access to the network-accessible resources on a networkwithin their security level clearance. In other words, network securitysecures the network by protecting and monitoring operations beingperformed on network-accessible resources.

SUMMARY

The illustrative embodiments herein provide a system for user activitycapturing and monitoring services. The invention has a server-clientarchitecture. The client side consists of an agent which performs singlesign-on actions for corresponding applications, and a few monitoringmodules which captures user activity and transfer activity data to theserver component. Each application workflow, determines the rightinterface and right step to perform single sign-on, and calls individualmonitoring modules to perform monitoring actions based on the nature ofthe application. Activities such as user login, logout, all keystroke,mouse click, and server response are captured and monitored. Eachactivity monitored by the modules is also logged in the database witheach session differentiated by a session identifiers.

For console access such as Secure Shell, multiple Secure Shell sessionsor nested Secure Shell sessions can be differentiated.

For graphical user interface applications, such as Tool for OracleApplication Developers (TOAD) for database access, Remote DesktopProtocol for remote Windows server access, activity logs are linked withwindow title, keystrokes, mouse clicks and critical screenshots. This isachieved via an event-driven snapshot taking mechanism which ensureshigh performance and low storage size. The resulted log is alsosearchable via title or command text.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a pictorial representation of a network of data processingsystems in which illustrative embodiments may be implemented;

FIG. 2 is a diagram of a data processing system depicted in accordancewith an illustrative embodiment;

FIG. 3 is an information technology delivery system depicted inaccordance with an illustrative embodiment;

FIG. 4 is an in depth information technology delivery system accordingto an illustrative embodiment;

FIG. 5 is a flow chart for command capturing within a profile accordingto an illustrative embodiment;

FIG. 6 is a data flow chart for command capturing within a monitoringmodule according to an illustrative embodiment;

FIG. 7 is a flowchart for activity capturing in a bitmapped consoleaccording to an illustrative embodiment;

FIG. 8 is a flowchart for activity capturing in a bitmapped consoleaccording to an illustrative embodiment;

FIG. 9 is flowchart of a process for capturing activity in a bitmappedconsole according to an illustrative embodiment;

FIG. 10 is a flowchart of a process for capturing activity in abitmapped console for a screenshot module according to an illustrativeembodiment;

FIG. 11 is flowchart for obtaining an event driven screenshot accordingto an illustrative embodiment;

FIG. 12 is an illustration of a series of audit logs according to anillustrative embodiment; and

FIG. 13 a flow chart for applying a policy to recorded event is shownaccording to an illustrative embodiment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module,” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

With reference now to the figures, and in particular, with reference toFIGS. 1-3, diagrams of data processing environments are provided inwhich illustrative embodiments may be implemented. It should beappreciated that the Figures are only meant as examples and are notintended to assert or imply any limitation with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environments may be made.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented.Network data processing system 100 is a network of computers and otherdevices in which the illustrative embodiments may be implemented.Network data processing system 100 contains network 102, which is themedium used to provide communications links between the computers andthe other various devices connected together within network dataprocessing system 100. Network 102 may include connections, such aswire, wireless communication links, or fiber optic cables.

In the depicted example, server 104 and server 106 connect to network102, along with storage unit 108. Server 104 may be, for example, anauditing server device that illustrative embodiments use to audit systemaudit logs of remote client devices to determine whether monitored useractivity on the remote client device associated with a work request wasin compliance with one or more regulations. A work request is a workorder or work instruction that typically is or includes incident,problem, or change ticket information regarding the remote clientdevice. The work request may either be automatically generated by theremote client device, itself, or may be manually generated by a user ofthe remote client device. The work request is used to have an identifiedproblem corrected on the remote client device by an end user on an enduser workstation device via network 102. A regulation may be, forexample, a federal regulation provided by FFIEC, HIPAA, or RTIA. FFIECis the Federal Financial Institutions Examination Council. FFIEC is aformal interagency body of the United States government empowered toprescribe uniform principles, standards, and report forms for thefederal examination of financial institutions. HIPAA is the HealthInsurance Portability and Accountability Act enacted by the UnitedStates, which addresses the security and privacy of healthcare data.RTIA is the Right to Information Act enacted by the Parliament of India,which allows access to access to government documents and information.

Server 106 may be, for example, a system log management server devicethat receives audit logs from a plurality of remote client devices. Theaudit logs of the remote client devices include the end user workstationdevice activities performed on the remote client devices to correct theproblems associated with the work requests. In addition, the system logmanagement server device may store the audit logs in the form of auditlog reports for each of the plurality of remote client devices. Further,server 104 and server 106 may each represent a plurality of serverdevices.

Storage unit 108 is a network storage device capable of storing data ina structured or unstructured format. The data stored in storage unit 108may be data of any type. Storage unit 108 may be, for example, anactivity logging database system that stores work request informationreceived from a plurality of remote client devices.

Clients 110, 112, and 114 also connect to network 102. Client computers110, 112, and 114 may be, for example, network server devices thatprovide IT services, such as financial services or medical services, toindividuals connected to network 102. The financial service may beregulated by FFIEC regulations and the medical service may be regulatedby HIPAA regulations, for example. However, it should be noted thatclient computers 110, 112, and 114 may provide other types of ITservices that may be regulated by other types of regulations. Aregulated IT service is a service that is not available for unrestrictednetwork access. For example, a medical services application may provideonline access to confidential medical history data that is protectedunder HIPAA regulations. Thus, access to and activities performed on aremote client device that stores this confidential medical data must bemonitored and audited to determine whether HIPAA regulations arecomplied with. An activity or task associated with a work requestperformed on a remote client device that stores confidential data maybe, for example, resetting a password, applying a new security patch,configuring a software application, or testing a hardware component.

In the depicted example, server computer 104 provides information, suchas boot files, operating system images, and applications to clientcomputers 110, 112, and 114. Client computers 110, 112, and 114 areclients to server computer 104 and server computer 106. Also, networkdata processing system 100 may include additional server computers,client computers, and other devices not shown.

Program code located in network data processing system 100 may be storedon a computer recordable storage medium and downloaded to a computer orother device for use. For example, program code may be stored on acomputer recordable storage medium on server 104 and downloaded toclient 110 over network 102 for use on client 110.

In the depicted example, network data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational, and other computer systems that route data and messages. Ofcourse, network data processing system 100 also may be implemented as anumber of different types of networks, such as for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIG. 1 isintended as an example, and not as an architectural limitation for thedifferent illustrative embodiments.

With reference now to FIG. 2, a diagram of a data processing system isdepicted in accordance with an illustrative embodiment. Data processingsystem 200 is an example of a computer, such as server 104 or client 110in FIG. 1, in which computer usable program code or instructionsimplementing processes of illustrative embodiments may be located. Inthis illustrative example, data processing system 200 includescommunications fabric 202, which provides communications betweenprocessor unit 204, memory 206, persistent storage 208, communicationsunit 210, input/output (I/O) unit 212, and display 214.

Processor unit 204 serves to execute instructions for softwareapplications or programs that may be loaded into memory 206. Processorunit 204 may be a set of one or more processors or may be amulti-processor core, depending on the particular implementation.Further, processor unit 204 may be implemented using one or moreheterogeneous processor systems, in which a main processor is presentwith secondary processors on a single chip. As another illustrativeexample, processor unit 204 may be a symmetric multi-processor systemcontaining multiple processors of the same type.

Memory 206 and persistent storage 208 are examples of storage devices216. A storage device is any piece of hardware that is capable ofstoring information, such as, for example, without limitation, data,program code in functional form, and/or other suitable informationeither on a transient basis and/or a persistent basis. Memory 206, inthese examples, may be, for example, a random access memory, or anyother suitable volatile or non-volatile storage device. Persistentstorage 208 may take various forms, depending on the particularimplementation. For example, persistent storage 208 may contain one ormore devices. For example, persistent storage 208 may be a hard drive, aflash memory, a rewritable optical disk, a rewritable magnetic tape, orsome combination of the above. The media used by persistent storage 208may be removable. For example, a removable hard drive may be used forpersistent storage 208.

Communications unit 210, in this example, provides for communicationwith other data processing systems or devices. In this example,communications unit 210 is a network interface card. Communications unit210 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 212 allows for the input and output of data with otherdevices that may be connected to data processing system 200. Forexample, input/output unit 212 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 212 may send output to a printer. Display 214provides a mechanism to display information to a user.

Instructions for the operating system, applications, and/or programs maybe located in storage devices 216, which are in communication withprocessor unit 204 through communications fabric 202. In thisillustrative example, the instructions are in a functional form onpersistent storage 208. These instructions may be loaded into memory 206for running by processor unit 204. The processes of the differentembodiments may be performed by processor unit 204 using computerimplemented instructions, which may be located in a memory, such asmemory 206. These instructions are referred to as program code, computerusable program code, or computer readable program code that may be readand run by a processor in processor unit 204. The program code, in thedifferent embodiments, may be embodied on different physical or computerreadable storage media, such as memory 206 or persistent storage 208.

Program code 218 is located in a functional form on computer readablemedia 220 that is selectively removable and may be loaded onto ortransferred to data processing system 200 for running by processor unit204. Program code 218 and computer readable media 220 form computerprogram product 222. In one example, computer readable media 220 may becomputer readable storage media 224 or computer readable signal media226. Computer readable storage media 224 may include, for example, anoptical or magnetic disc that is inserted or placed into a drive orother device that is part of persistent storage 208 for transfer onto astorage device, such as a hard drive, that is part of persistent storage208. Computer readable storage media 224 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 200. In someinstances, computer readable storage media 224 may not be removable fromdata processing system 200.

Alternatively, program code 218 may be transferred to data processingsystem 200 using computer readable signal media 226. Computer readablesignal media 226 may be, for example, a propagated data signalcontaining program code 218. For example, computer readable signal media226 may be an electro-magnetic signal, an optical signal, and/or anyother suitable type of signal. These signals may be transmitted overcommunication links, such as wireless communication links, an opticalfiber cable, a coaxial cable, a wire, and/or any other suitable type ofcommunications link. In other words, the communications link and/or theconnection may be physical or wireless in the illustrative examples. Thecomputer readable media also may take the form of non-tangible media,such as communication links or wireless transmissions containing theprogram code.

In some illustrative embodiments, program code 218 may be downloadedover a network to persistent storage 208 from another device or dataprocessing system through computer readable signal media 226 for usewithin data processing system 200. For instance, program code stored ina computer readable storage media in a server data processing system maybe downloaded over a network from the server to data processing system200. The data processing system providing program code 218 may be aserver computer, a client computer, or some other device capable ofstoring and transmitting program code 218.

The different components illustrated for data processing system 200 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to, or in place of, those illustrated for dataprocessing system 200. Other components shown in FIG. 2 can be variedfrom the illustrative examples shown. The different embodiments may beimplemented using any hardware device or system capable of executingprogram code. As one example, data processing system 200 may includeorganic components integrated with inorganic components and/or may becomprised entirely of organic components excluding a human being. Forexample, a storage device may be comprised of an organic semiconductor.

As another example, a storage device in data processing system 200 isany hardware apparatus that may store data. Memory 206, persistentstorage 208, and computer readable media 220 are examples of storagedevices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 202 and may be comprised of one or more buses, such as a systembus or an input/output bus. Of course, the bus system may be implementedusing any suitable type of architecture that provides for a transfer ofdata between different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 206 or a cache such asfound in an interface and memory controller hub that may be present incommunications fabric 202.

The illustrative embodiments herein provide a system for user activitycapturing and monitoring services. The invention has a server-clientarchitecture. The client side consists of an agent which performs singlesign-on actions for corresponding applications, and a few monitoringmodules which are exported as dynamic link library application programinterfaces. Each application workflow, determines the right interfaceand right step to perform single sign-on, and calls individualmonitoring modules to perform monitoring actions based on the nature ofthe application. Activities such as user login, logout are logged onserver audit log database by default. Each activity monitored by themodules is also logged in the database with each session differentiatedby a session identifiers.

Activities such as Secure Shell are captured when the command isentered. A separate session identifiers is assigned to the Secure Shellsession to differentiate it from the parent session. So that multipleSecure Shell sessions or nested Secure Shell sessions can bedifferentiated.

For graphical user interface applications, such as Tool for OracleApplication Developers (TOAD) for database access, Remote DesktopProtocol for remote Windows server access, activity logs are linked withwindow title, keystrokes, mouse clicks and critical screenshots. This isachieved via an event-driven snapshot taking mechanism which ensureshigh performance and low storage size. The resulted log is alsosearchable via title or command text.

Referring now to FIG. 3, an information technology delivery system isshown according to an illustrative embodiment. System 300 is a networkdata processing system, such as network data processing system 100 ofFIG. 1.

System 300 includes integrated management system server 310. Integratedmanagement system server 310 is a server such as one of servers 104 orserver 106 of FIG. 1. Integrated management system server 310 is acentral repository for user data, user access profiles, identitywallets, and machine profiles. Integrated management system server 310provides a Web based interface to administrate users and policies.

Integrated management system server 310 provides a central point ofadministration and control. Integrated management system server 310enables centralized management of user identities, application specificworkflows, and authentication policies. Integrated management systemserver 310 also provides loss management of authentication tokens,certificate management, and audit management Administratordesktop/gateway 312 includes base agent 314. Base agent 314 is asoftware component that can identify and notify common problems withapplications 315 on endpoint systems 316 that are monitored by baseagent 314.

Administrator desktop/gateway 312 includes application workflow/profile318. Application workflow/profile 318 is a set of instructions thathandles workflow automation for supported desktop applications onendpoint systems 316. In one illustrative embodiment, applicationworkflow/profile 318 is constructed as a state engine, consisting ofstates, triggers, and actions. Application workflow/profile 318 cancontain instructions for performing automatic operations for user logon,user logoff, user change or reset password, and other customizedactivities the application might present. Application workflow/profile318 might consist of any combination of these activities and moredepending on business requirements and users' needs.

In one illustrative embodiment, application workflow/profile 318 isassociated with and uniquely mapped to only one application. Anapplication can be an executable file (.EXE) or a web page, each ofwhich is a unique process on endpoint system 316. Applicationworkflow/profile 318 is loaded in runtime and begins its automationworkflow when application workflow/profile 318 detects that the relativeapplication is initiated on endpoint system 316.

Administrator desktop/gateway 312 includes monitoring module 320.Monitoring module 320 is one or more software modules that log eventmessages to audit log server 322. The event messages can be, for examplebut not limited to, state changes detected by application specificworkflow 420 or monitoring workflow 432. Events are provided to serveraudit log server 322 in audit logs 324.

Audit log server 322 is a server such as one of servers 104 or server106 of FIG. 1.

Audit log server 322 includes application/user policies 324 andmonitoring policies 326. Application/user policies 324 and monitoringpolicies 326 may define, for example, which user commands are blockedand which user commands are allowed, which user activities are recordedin a system audit log and which user activities are not, and which useractivities require immediate action.

Audit log server 322 includes audit logs 328 provided by monitoringmodule 320. Audit logs 328 are records of user and administrationactivity, as determined by application specific workflows and monitoringworkflow.

Referring now to FIG. 4, an in depth information technology deliverysystem is shown according to an illustrative embodiment. System 400 issystem 300 of FIG. 3.

Agent 410 is a client side software system that communicates with, andperforms tasks for, the integrated management system server 412.Communication and tasks can be performed to synchronize data changeswith integrated management system server 412. In one illustrativeembodiment, agent 410 can cache data locally (on disk) based onpolicies, such as application policy 414 and monitoring policy 416.Application policy 414 is one or more of application/user policies 324of FIG. 3. Monitoring policy 416 is one or more of monitoring policies326 of FIG. 3. As such, agent 410 is able to perform most of itsfunctions even if it is not connected to integrated management systemserver 412 at any point in time.

Agent 410 is responsible for authenticating a user. Because of its localcache, agent 410 can automate single sign-on into operating system 418and to a set of applications that are defined in application specificworkflow 420. Agent 410 can extend the Windows Graphical Identificationand Authentication (GINA) dynamic link library chain to provideadditional functions for self-service or strong authentication.

Integrated management system server 412 is integrated management systemserver 310 of FIG. 3. Integrated management system server 412 is acentral repository for user data, user access profiles, identitywallets, and machine profiles. Integrated management system server 412provides a Web based interface to administrate users and policies.

Integrated management system server 412 provides a central point ofadministration and control. Integrated management system server 412enables centralized management of user identities, application specificworkflow 420, and authentication policies. Integrated management systemserver 412 also provides loss management of authentication tokens,certificate management, and audit management.

Wallet 422 holds the user credentials that are required for singlesign-on. Wallet 422 is loaded from the integrated management systemserver 412 into the agent 410 after successful authentication of theuser so that wallet 422 is available even when the endpoint isdisconnected from the computer network. To protect the credentialsagainst tampering or stealing, wallet 422 is encrypted with a strongencryption mechanism.

Agent 410 includes plug-ins 424. Plug-ins 424 are blocks of code thatperform some custom action needed as part of a workflow trigger orworkflow action inside application specific workflow 420. In oneillustrative embodiment, can be for example but not limited to, VBScriptor JavaScript. Using the user's access privileges, plug-ins 424 can makecalls into operating system 418, as well as into other ones of plug-ins424.

Agent 410 typically uses plug-ins 424 to implement customizedauthentication, access control, or workflow automation for a specificapplication. This customized authentication, access control, or workflowautomation can include, but is not limited to, retrieving applicationcredential from wallet 422, retrieving a user policy setting from wallet422, looking up a user's group membership or attribute from a userdirectory, reading or storing data from a central fileshare, looking upthe time from the host system clock, performing an additional checksumor check the installation path on a target application prior to singlesign-on, calling an external application or process, and making an HTTPScall to a third-party service.

Agent 410 includes observer layer 426. Observer layer 426 is a softwarecomponent that performs necessary logon/logoff and automation actionsinto various applications run by system 400. When an applicationpresents a request for credentials, observer layer 426 is responsiblefor the appropriate action.

In one illustrative embodiment, observer layer 426 is composed of a coremodule and a number of agent instances that are hooked into variousapplications. The applications can include, for example but not limitedto, for example, IBM Lotus® Notes® application, Microsoft Outlook®, andMicrosoft Internet Explorer®. The behavior of the number of agentinstances within each application is driven by application specificworkflow 420.

Automated trigger layer 428 and automated trigger layer 430 causetransitions between states in application specific workflow 420.Automated trigger layer 428 and automated trigger layer 430 define whena condition is true. For example, automated trigger layer 428 andautomated trigger layer 430 can define when a Windows executable windowis created, when a Web document completes loading, when an HTML elementis clicked, and when an operating system executable button within agraphical user interface is clicked.

Application specific workflow 420 is application/workflow profile 318 ofFIG. 3. Application specific workflow 420 is a set of instructions thathandles workflow automation for supported applications in operatingsystem 418. In one illustrative embodiment, application specificworkflow 420 is constructed as a state engine, consisting of states,triggers, and actions. Application specific workflow 420 can containinstructions for performing automatic operations for user logon, userlogoff, user change or reset password, and other customized activitiesthe application might present. Application specific workflow 420 mightconsist of any combination of these activities and more depending onbusiness requirements and users' needs. In one illustrative embodiment,application specific workflow 420 is an XML-structured file thatprovides a declarative set of pre-conditions that can be detected byautomated trigger layer 428 and automated trigger layer 430 to causetransitions between states in application specific workflow 420.

In one illustrative embodiment, application specific workflow 420 isassociated with and uniquely mapped to only one application. Anapplication can be an executable file (.EXE) or a web page, each ofwhich is a unique process on an endpoint system or administratordesktop/gateway. The endpoint system can be, for example, endpointsystem 316 of FIG. 3. The administrator desktop/gateway can be, forexample, administrator desktop/gateway 312 of FIG. 3.

Application specific workflow 420 is loaded in runtime and begins itsautomation workflow when application specific workflow 420 detects thatthe relative application is initiated on an endpoint system oradministrator desktop/gateway. The endpoint system can be, for example,endpoint system 316 of FIG. 3. The administrator desktop/gateway can be,for example, administrator desktop/gateway 312 of FIG. 3.

Monitoring workflow 432 is a set of instructions that provide workflowautomation applications. Monitoring workflow 432 detects changes to theposition or title of the current active window, or a mouse or keyboardevent. When such event is detected, monitoring workflow 432 gives acallback to one of set of triggers 441.

Set of triggers 441 can include, for example, command capturing forconsole access trigger 442. Set of triggers 441 can include, forexample, activity logging for bitmapped console trigger 444. Set oftriggers 441 can include, for example, activity logging for GUIapplications trigger 446.

Monitoring components 433 are software modules, such as for example butnot limited to, application programming interface applications that logevent messages to integrated management system server 412. The eventmessages can be, for example but not limited to, state changes detectedby application specific workflow 420 or monitoring workflow 432. Eventsare provided to server 412 in audit logs 448.

Monitoring component 433 can include for example, bitmap recognitionmodule 434. In one illustrative embodiment, the bitmap recognitionmodule 434 comprises an optical character recognition module to capturebit-mapped application processes.

Monitoring component 433 can include for example, screen capturingmodule 436. In one illustrative embodiment, screen capturing module 436dynamically captures application screenshots based on user input thatcauses a state change within either application specific workflow 420 ormonitoring workflow 432.

Monitoring component 433 can include for example, graphical userinterface module 438. In one illustrative embodiment, graphical userinterface module 438 dynamically captures a window title of a currentactive application as well as any button name that is interacted with inthe graphical user interface as an activity signature. In oneillustrative embodiment, graphical user interface module 438 can includea trigged when though a window monitoring process to trigger a log onprocess.

Monitoring component 433 can include for example, command and responsemodule 440. In one illustrative embodiment, command and response module440 captures user input, such as but not limited to, key strokes andmouse clicks.

Audit logs 448 are records of user and administration activity, asdetermined by application specific workflow 420 and monitoring workflow432 that are stored in integrated management system server 412.

Audit logs 448 can provide logs of different activity. For example,audit logs may provide a logged record of user, system, andadministrator activities. User and administrator logs track user,administrator, and help desk activity. The user and administrator logsare considered the audit logs, and are written to integrated managementsystem server 412. The system logs are message and error logs forintegrated management system server 412 itself, primarily used fortroubleshooting server issues and monitoring the system health.

Triggers 441 are software mechanisms that detect an occurrence of anevent defined by one of application specific workflow 420 or monitoringworkflow 432. In response to detecting the event, triggers 441 thencause the creation of audit log 448.

In one illustrative embodiment, trigger 442 is a command capturing forconsole access. When a user attempts a log on process, trigger 442invokes one or more of monitoring components 433.

In one illustrative embodiment, trigger 444 is an activity logger forbitmapped console applications. In response to determining a change by abitmapped recognition module, trigger 444 invokes one or more ofmonitoring components 433.

In one illustrative embodiment, trigger 446 is an activity logger forapplications' graphical user interfaces. In response to detecting aninteraction with an icon or other graphical user interface element,trigger 446 invokes one or more of monitoring components 433.

Referring now to FIG. 5, a flow chart for command capturing within aprofile is shown according to an illustrative embodiment. Process 500 isa software process, executing on a software component, such asapplication specific workflow 420 of FIG. 4.

Process 500 begins when an application is opened on an endpoint systemor administrator desktop/gateway (step 510). The application can be, forexample, one of applications 315 of FIG. 3. The endpoint system can be,for example, endpoint system 316 of FIG. 3. The administratordesktop/gateway can be, for example, administrator desktop/gateway 312of FIG. 3.

Process 500 then performs identification injection, capturing, andcheckout (step 520). Identification injection, capturing, and checkoutis a process that retrieves any necessary user credentials that arerequired for access of an application, and applies those credentials toa checkout procedure. The credentials can be stored in a wallet, such aswallet 422 of FIG. 4. Process 500 then generates a session identifier(step 530). The session identifier is a unique identifier that is sentwith each request made by the logged on user.

Process 500 then captures a hostname and internet protocol address (step540).

Process 500 then captures the application process identification (step550).

Process 500 then makes a call to a monitoring module, transferring thecaptured information (step 560). The monitoring module can be, forexample, monitoring components 433 of FIG. 4.

Responsive to making the call to the monitoring module, process 500continues with any regular workflow (step 570), with the processterminating thereafter.

Referring now to FIG. 6, a data flow chart for command capturing withina monitoring module is shown according to an illustrative embodiment.Monitoring module 600 is one of monitoring components 433 of FIG. 4.

Monitoring module 600 logs session identifier, user identifier,hostname, internet protocol address, application name calls a privilegeidentification manager (610).

Monitoring module receives user input (620), and then captures anyserver response (630). The server response can be sequentially capturedinto a same buffer as the user input.

Monitoring module then logs the session identifiers, along with thesequential user input and server response.

In one illustrative embodiment, the buffer is split into 500-bytechunks. The size is chosen due to a 512 byte of the description field ina user activity log table.

Monitoring module 600 logs session id, and log data chunk (640). If theprivilege identification dies, monitoring module 600 terminatesmonitoring.

The session identifier identifies the specific cache entry for thatuser.

Referring now to FIG. 7, a flowchart for activity capturing in abitmapped console is shown according to an illustrative embodiment.Process 700 is a software process, executing on a software component,such as in a command policy of an integrated management server system,such as integrated management server system 412 of FIG. 4. The commandpolicy can be, for example, one of application specific workflow 420 ormonitoring workflow 432 of FIG. 4.

Process 700 triggers a screenshot upon the occurrence of a trigger. Thetrigger can be, for example, one of triggers 441 of FIG. 4.

Responsive to the trigger determining a keystroke, a screenshot of thebitmapped console is triggered (step 710). The keystroke can be, forexample, a depress of the “enter/return” key.

Responsive to the trigger determining a mouse click, a screenshot of thebitmapped console is triggered (step 720). Process 700 then returns tostep 710 in an iterative manner log additional activities.

Referring now to FIG. 8, a flowchart for activity capturing in abitmapped console is shown according to an illustrative embodiment.Process 800 is a software process, executing on a software component,such as in a profile of an integrated management server system, such asintegrated management server system 412 of FIG. 4. The profile can be,for example, one of application specific workflow 420 or monitoringworkflow 432 of FIG. 4. The profile can be a profile for a bitmappedconsole, such as a remote desktop profile.

Process 800 begins when an application is opened on an endpoint systemor administrator desktop/gateway (step 810). The application can be, forexample, one of applications 315 of FIG. 3. The endpoint system can be,for example, endpoint system 316 of FIG. 3. The administratordesktop/gateway can be, for example, administrator desktop/gateway 312of FIG. 3.

Process 800 then performs identification injection, capturing, andcheckout (step 820). Identification injection, capturing, and checkoutis a process that retrieves any necessary user credentials that arerequired for access of an application, and applies those credentials toa checkout procedure. The credentials can be stored in a wallet, such aswallet 422 of FIG. 4.

Process 800 then generates a session identifier (step 830). The sessionidentifier is a unique identifier that is sent with each request made bythe logged on user.

Process 800 then captures a hostname and internet protocol address (step840).

Process 800 then makes a log entry, logging the captured information(step 850). The logging information can be transferred as audit logs 448of FIG. 4.

Process 800 then retrieves a screenshot trigger policy from theintegrated management server (step 860). The screenshot trigger policycan be one of application policy 414 of FIG. 4 or monitoring policy 416of FIG. 4.

For each trigger, process 800 calls the screenshot module (step 870),with the process terminating thereafter.

While FIG. 8 refers to calling the screenshot module, it is understoodthat the screenshot module can be incorporated into or combined withother modules. For example, the screenshot may be taken the detectionmodule, such as the detection module described in FIG. 9. Furthermore,it is understood that the capture may be constrained by some conditions,such as, for example but not limited to, that a screenshot of should betaken only if only if certain windows are visible on a user's desktop.

Referring now to FIG. 9, a flowchart of a process for capturing activityin a bitmapped console is shown according to an illustrative embodiment.Process 900 is a software process, executing on a software component,such as monitoring module 432 of FIG. 4.

Process 900 begins when a session identifier is received (step 910). Thesession identifier can be received in response to the name of the RemoteDesktop's address.

Process 900 determines the active window (step 920). An active window isthe currently focused window in the current window manager or explorer.The active window can be the window that is currently being used by theuser.

Process 900 extracts the active window title (step 930). The windowtitle for the active window is text that appears within a title bar atthe top of the active window.

Process 900 determines any change to the window title (step 940).Changes to the window title can be determined by performing opticalcharacter recognition to the title bar of the active window, andcomparing detected text to previous recognized window.

Process 900 then records user input (step 950). User input can be forexample but not limited to, key strokes and mouse clicks.

Process 900 then calls the screenshot module (step 960).

Process 900 and extracts any text around a mouse click position (step970).

Process 900 then logs the screenshot along with the session identifier,as well as all captured text and extracted text (step 980), with theprocess terminating thereafter.

Referring now to FIG. 10, a flowchart of a process for capturingactivity in a bitmapped console for a screenshot module is shownaccording to an illustrative embodiment. Process 1000 is a softwareprocess, executing on a software component, such as monitoring module432 of FIG. 4.

Process 1000 begins by receiving a call from another monitoring module(step 1010). The call can be, for example a call such as the call ofstep 870 of FIG. 8. The call can include a session identifier for thetriggered application.

Process 1000 takes a screenshot of the desired window (step 1020). Thedesired window is the graphical user interface into which a user actionwas entered, and detected. The desired can be, for example the activewindow. For example, the screenshot can include the entire remotedesktop profile.

Process 1000 converts and compresses the screenshot into a storageformat (step 1030). In one illustrative embodiment, the storage formatcan be, for example, but not limited to, a binary format.

Process 1000 then applies a data encoding compression to the screenshot(step 1040). According to one illustrative embodiment, a lossycompression can be applied to a background of the screenshot, while alossless compression is applied to the foreground. The foreground of thescreenshot can include, for example but not limited to, the activewindow. The background of the screenshot can include, for example butnot limited to, other windows or icons visible within the screenshot notincluding the active window. Lossless compression use data compressionalgorithms that allows for exact reconstruction of the foreground fromcompressed data. However, lossy compression does not produce an exactreconstruction of the background from the compressed data.

Process 1000 then performs an XOR operation with a preview screenshot toextract a delta between the two screenshot (step 1050).

Process 1000 then log the session identifier and image fits (step 1060),with the process terminating thereafter. The image fits include at leastthe delta file.

Referring now to FIG. 11, a flowchart for is an event driven screenshotis shown according to an illustrative embodiment.

Process 1100 begins by receiving an initial workflow (step 1105). Theinitial workflow is application specific workflow 420 or monitoringworkflow 432 of FIG. 4.

Responsive to receiving the initial workflow, process 1100 forwards theinitial workflow to an optical character recognition module (step 1110)and begins monitoring by following the visual activity of the screenimage and/or the user's use of mouse and keyboard. In one illustrativeembodiment, the detection of mouse clicks and keyboard events isperformed externally from VOP, such as for example, but not limited to,by an application such as IBM Tivoli Access Manager for EnterpriseSingle Sign-On (TAMESSO).

Process 1100 then detects an event (step 1115). The event can bedetected by the triggering of a trigger, such as one of triggers 441 ofFIG. 4.

In response to the event being a change to a change of caption (step1120), process 1100 captures a screenshot (step 1125). The screenshotcan be captured according to process 1000 of FIG. 10.

Responsive to capturing the screenshot, process 1100 logs the sessionid, and any recorded keystroke or mouse events (step 1030), with theprocess terminating thereafter. The session id and the recordedkeystroke or mouse events can be logged as audit logs 448 of FIG. 4.

Returning now to step 1115, responsive to the event being a mouse click(step 1135), process 1100 captures the event (step 1140). By capturingthe mouse click event, process 1100 stores the metadata associated withthe event, such as for example but not limited to, a kind of the mouseclick, a position of the pointer, and a button identification that isutilized for the click.

Process 1145 then captures a screenshot (step 1145). The screenshot canbe captured according to process 1000 of FIG. 10.

Process 1100 forwards the event to the monitored application (step1150). In one illustrative embodiment, the mouse monitoring adds a setof hooks to mouse handling chain of the operating system. When a mouseevent is triggered, the “hook” captures or does something with theevent, for example reads metadata associated with the mouse event. Thehook then releases the event back to the event chain. In this manner themonitoring will not interfere the processing, just delay it marginally.

Process 1100 waits for image stabilization (step 1155), as describedabove. Waiting for “Image stabilization” means waiting for certainprocesses to complete. When a screen image is updated, the image doesnot usually refresh instantly, but rather refreshes in a sweepingmanner. Furthermore, sometimes a graphical user interface might takesome time to load it graphics. Some content is shown immediately, forexample but not limited to menus, while other content takes some time tobe retrieved. By waiting for “Image stabilization,” process 1100 waitsfor the whole screen image or part of the screen image not to change anymore.

Returning now to step 1115, responsive to the event being a change tothe keyboard state machine (step 1160), process 1100 determines if thechange to the state machine was due to a keystroke of a target key (step1165). The keystroke of a target key can be, for example, a depress ofthe “enter/return” key. Responsive to determining that change to thestate machine was due to a keystroke of a target key (“yes” at step1165), process 1100 proceeds to step 1140 to capture the event.

Responsive to determining that change to the state machine was not dueto a keystroke of a target key (“no” at step 1165), process 1100 thendetermines whether a predetermined time has passed since the last keypress (step 1170). Responsive to determining that the time passed sincethe last key press is less than some predetermined (“less thanthreshold” at step 1170), process 1100 iterates back to step 1160.

Responsive to determining that the time passed since the last key pressis larger than some predetermined (“larger than threshold” at step1170), process 1100 proceeds to proceeds to step 1140 to capture theevent.

Referring now to FIG. 12, an illustration of a series of audit logs isshown according to an illustrative embodiment. Audit logs 1200 are auditlogs such as audit logs 448 of FIG. 4.

Audit logs 1210-1216 are audit logs of graphical user interface andbitmapped applications. The console applications can be applicationssuch as applications 315 of FIG. 3.

Audit log 1210 is an audit log taken at time indicated by timestamp T1.Audit log 1210 includes a session identifier, a user identifier, asystem identifier, an application identifier, and a server identifier.This information can be captured by monitoring components, such asMonitoring components 433 of FIG. 4. Additionally, audit log 1210includes an indication of the action triggering the audit log. Here, alogin action by user U triggers audit log 1210.

Audit log 1212 is an audit log taken at time indicated by timestamp T2.Audit log 1212 includes a session identifier. This information can becaptured by monitoring components, such as monitoring components 433 ofFIG. 4. Additionally, audit log 1212 includes an indication of theaction triggering the audit log. Here, a command input into “windowtitle” of “xyz” by user U triggers audit log 1212.

Audit log 1212 also includes a screenshot of “window title” at timeindicated by timestamp T2. The screenshot can be determined, forexample, by process 1000 of FIG. 10.

Audit log 1214 is an audit log taken at time indicated by timestamp T3.Audit log 1214 includes a session identifier. This information can becaptured by monitoring components, such as Monitoring components 433 ofFIG. 4. Additionally, audit log 1214 includes an indication of theaction triggering the audit log. Here, a “left mouse click” of “buttonname” within “window title” by user U triggers audit log 1214.

Audit log 1214 also includes a screenshot of “window title” at timeindicated by timestamp T32. The screenshot can be determined, forexample, by process 1000 of FIG. 10.

Audit log 1216 is an audit log taken at time indicated by timestamp T4.Audit log 1216 includes a session identifier. This information can becaptured by monitoring components, such as Monitoring components 433 ofFIG. 4. Additionally, audit log 1216 includes an indication of theaction triggering the audit log. Here, a close of window of themonitored application triggers audit log 1216.

Audit logs 1218-1224 are audit logs of console applications. The consoleapplications can be applications such as applications 315 of FIG. 5.

Audit log 1218 is an audit log taken at time indicated by timestamp T5.Audit log 1218 includes a session identifier, a user identifier, asystem identifier, an application identifier, and a server identifier.This information can be captured by monitoring components, such asmonitoring components 433 of FIG. 4. Additionally, audit log 1218includes an indication of the action triggering the audit log. Here, alogin action by user U triggers audit log 1218.

Audit log 1220 is an audit log taken at time indicated by timestamp T6.Audit log 1220 includes a session identifier. This information can becaptured by monitoring components, such as monitoring components 433 ofFIG. 4. Additionally, audit log 1220 includes an indication of theaction triggering the audit log and any server response. Here, a commandof “xyz” by user U and a server response of “abc” triggers audit log1220.

Audit log 1222 is an audit log taken at time indicated by timestamp T7.Audit log 1222 includes a session identifier. This information can becaptured by monitoring components, such as monitoring components 433 ofFIG. 4. Additionally, audit log 1222 includes an indication of theaction triggering the audit log and any server response. Here, a commandof “xyz” by user U and a server response of “abc” triggers audit log1222.

Audit log 1224 is an audit log taken at time indicated by timestamp T8.Audit log 1224 includes a session identifier. This information can becaptured by monitoring components, such as monitoring components 433 ofFIG. 4. Additionally, audit log 1224 includes an indication of theaction triggering the audit log. Here, a close of window of themonitored application triggers audit log 1216.

Referring now to FIG. 13, a flow chart for applying a policy to recordedevent is shown according to an illustrative embodiment. Process 1300 isa software process, executing on a software component, such asapplication specific workflow 420 of FIG. 4.

Process 1300 begins by receiving data from a client (step 1310). Thedata can include, for example, a screenshot along with any associatedmouse event or keyboard event.

Process 1300 then retrieves a security policy (step 1320). The securitypolicy can be, for example, a policy such as application policy 414 andmonitoring policy 416.

Process 1300 then determines applies a pattern-matching algorithm to thedata received from the client, according to security policy (step 1330).Based on results from the pattern matching algorithm, process 1300 canrecord the data (step 1340), record the data and raise alert to securityteam (step 1350), or record the data and terminate the client (step1360). Process 1300 terminates thereafter.

Thus, the illustrative embodiments herein provide a system for useractivity capturing and monitoring services. The invention has aserver-client architecture. The client side consists of an agent whichperforms single sign-on actions for corresponding applications, and afew monitoring modules which are exported as dynamic link libraryapplication program interfaces. Each application workflow, determinesthe right interface and right step to perform single sign-on, and callsindividual monitoring modules to perform monitoring actions based on thenature of the application. Activities such as user login, logout arelogged on server audit log database by default. Each activity monitoredby the modules is also logged in the database with each sessiondifferentiated by a session identifiers.

Activities such as Secure Shell are captured when the command isentered. A separate session identifiers is assigned to the Secure Shellsession to differentiate it from the parent session. Multiple SecureShell sessions or nested Secure Shell sessions can be differentiated.

For graphical user interface applications, such as Tool for OracleApplication Developers (TOAD) for database access, Remote DesktopProtocol for remote Windows server access, activity logs are linked withwindow title, keystrokes, mouse clicks and critical screenshots. This isachieved via an event-driven snapshot taking mechanism which ensureshigh performance and low storage size. The resulted log is alsosearchable via title or command text.

Thus, illustrative embodiments of the present invention provide acomputer implemented method, data processing system, and computerprogram product for controlling point in time access to a remote clientdevice and auditing system logs of the remote client device by anauditing server device to determine whether monitored user activity onthe remote client device associated with a work request was incompliance with one or more regulations. The flowchart and blockdiagrams in the Figures illustrate the architecture, functionality, andoperation of possible implementations of systems, methods and computerprogram products according to various embodiments of the presentinvention. In this regard, each block in the flowchart or block diagramsmay represent a module, segment, or portion of code, which comprises oneor more executable instructions for implementing the specified logicalfunction(s). It should also be noted that, in some alternativeimplementations, the functions noted in the block might occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to explain best theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer implemented method for capturing andmonitoring user activity, the computer implemented method comprising:identifying, by a client device, a monitored event within a workflow fora supported application providing a regulated service; responsive to theclient device identifying the monitored event, capturing, by the clientdevice, information about the monitored event, wherein the informationincludes a server response to the monitored event; waiting, by theclient device, for image stabilization of a whole screen image afterprocesses of the monitored event complete and the whole screen imagedoes not change any more before capturing a screenshot of the supportedapplication providing the regulated service; responsive to the imagestabilization of the whole screen image after the processes of themonitored event complete, capturing, by the client device, thescreenshot of the supported application providing the regulated service;applying, by the client device, a lossless data compression to aforeground of the screenshot that includes an active window of thesupported application providing the regulated service and applying, bythe client device, a lossy data compression to a background of thescreenshot that includes other windows and icons visible in thescreenshot but excludes the active window; associating, by the clientdevice, the information with the screenshot; storing, by the clientdevice, the associated information and screenshot as an audit log of themonitored event; and forwarding, by the client device, the audit log toan integrated management system server to determine that the audit logof the monitored event is in compliance with a regulation correspondingto the supported application providing the regulated service, whereinthe client device includes a client side agent that is a client sidesoftware system that communicates with and performs tasks to synchronizedata changes with the integrated management system server, and whereinthe workflow is one of an application specific workflow or a monitoringworkflow.
 2. The computer implemented method of claim 1, wherein theclient side agent includes plug-ins, the computer implemented methodfurther comprising: performing, by the client device, a custom actionneeded as part of a workflow trigger or workflow action inside anapplication specific workflow; and making, by the client device, callsinto an operating system or other ones of the plug-ins to implementcustomized authentication, access control, or workflow automation for aspecific application, wherein the customized authentication, accesscontrol, or workflow automation is selected from a group consisting ofretrieving an application credential from a wallet, retrieving a userpolicy setting from the wallet, looking up a user's group membership,looking up an attribute from a user directory, reading data from acentral fileshare, storing data to the central fileshare, looking up atime from a host system clock, performing an additional checksum on atarget application prior to single sign-on, performing a check of aninstallation path on a target application prior to single sign-on,calling an external application, calling an external process, and makingan HTTPS call to a third-party service.
 3. The computer implementedmethod of claim 1, wherein the monitored event is a state changedetected by the workflow, the state change selected from a groupconsisting of a change to a position of a current active window event, achange to a title of the current active window event, a mouse event, anda keyboard event.
 4. The computer implemented method of claim 1, whereinthe information is identified by a set of application programminginterface applications that log event messages to the integratedmanagement system server, the set of application programming interfaceapplications being selected from a group consisting of a bitmaprecognition module comprising an optical character recognition module tocapture bit-mapped application processes, a screen capturing module todynamically capture the screenshot of the supported applicationproviding the regulated service based on user input that causes a statechange within the workflow, and a graphical user interface module todynamically capture an activity signature, the activity signaturecomprising a window title of a current active application and a buttonname that is interacted with in a graphical user interface.